Intelligent distributed ledger consent optimizing apparatus for Asset Transfer

ABSTRACT

Aspects of the disclosure relate to processing asset transfers. A computing platform may receive an asset transfer request and extract information from it. The computing platform may modify a distributed ledger to include a new block corresponding to the asset transfer request. The computing platform may identify a consensus method by identifying, for each of a plurality of consensus methods, a subset of blocks from the distributed ledger that, when used to execute the corresponding consensus method, result in a lowest energy consumption value in comparison to remaining subsets of blocks. The computing platform may execute each consensus method using the corresponding identified subset of blocks, which may result in establishing consensus to process the asset transfer request. Based on establishing the consensus, the computing platform may direct an event processing platform to process the asset transfer request, which may cause the event processing platform to process the request accordingly.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority to U.S. patent application Ser. No.17/335,660, filed Jun. 1, 2021, and entitled “Intelligent DistributedLedger Consent Optimizing Apparatus for Asset Transfer,” which is herebyincorporated herein by reference in its entirety.

BACKGROUND

Aspects of the disclosure relate to processing asset transfer requests.In particular, one or more aspects of the disclosure relate toprocessing asset transfer requests using a distributed ledger.

In some instances, consensus among blocks of a distributed ledger may beused to validate and approve new blocks. In some instances, however, theprocess of obtaining such consensus may be inefficient and may requiresignificant processing resources to perform. Accordingly, as distributedledgers are increasingly adopted, it may be important to improvecorresponding efficiencies.

SUMMARY

Aspects of the disclosure provide effective, efficient, scalable, andconvenient technical solutions that address and overcome the technicalproblems associated with performing asset transfers. In accordance withone or more embodiments of the disclosure, a computing platformcomprising at least one processor, a communication interface, and memorystoring computer-readable instructions may receive an asset transferrequest. The computing platform may extract, using deep learning basedoptical character recognition (OCR), information from the asset transferrequest. The computing platform may identify a mining cluster for astored distributed ledger. The computing platform may modify, using themining cluster, the stored distributed ledger to include a new blockcorresponding to the asset transfer request. The computing platform mayidentify a consensus method by identifying, for each of a plurality ofconsensus methods, a subset of blocks from the stored distributed ledgerthat, when used to execute the corresponding consensus method, result ina lowest energy consumption value in comparison to remaining subsets ofblocks. The computing platform may execute each of the plurality ofconsensus methods using the corresponding identified subsets of blocks.The computing platform may establish, based on execution of each of theplurality of consensus methods, consensus to process the asset transferrequest. Based on establishing the consensus, the computing platform maysend one or more commands directing an event processing platform toprocess an event corresponding to the asset transfer request, which maycause the event processing platform to process the event.

In one or more instances, the information may include one or more of: afinancial institution corresponding to the asset transfer request, anamount of the asset transfer, a recipient account, or an originatoraccount. In one or more instances, the computing platform may identify,using the information and a stored list of authenticated financialinstitutions, whether or not the financial institution corresponding tothe asset transfer request is authenticated. Based on identifying thatthe financial institution corresponding to the asset transfer request isnot authenticated, the computing platform may send an authenticationrequest to an administrator computing device. Based on identifying thatthe financial institution corresponding to the asset transfer request isauthenticated, the computing platform may proceed to establish whetheror not the asset transfer request is genuine.

In one or more examples, establishing whether or not the asset transferrequest is genuine may include identifying whether or not the originatoraccount includes sufficient assets to perform the asset transfer. In oneor more examples, based on identifying that the asset transfer requestis not genuine, the computing platform may block the asset transfer.Based on identifying that the asset transfer request is genuine, thecomputing platform may perform the generation of the new block.

In one or more instances, the plurality of consensus methods may includeone or more of: proof of work, proof of stake, proof of elapsed time,raft, proof of importance, proof of authority, proof of activity, proofof capacity, or proof of burn. In one or more instances, each subset ofblocks may include a minimum number of blocks needed to establishconsensus using the corresponding consensus method.

In one or more examples, the computing platform may store, in agoverning block of the stored distributed ledger and after identifyingthe minimum numbers of blocks needed to establish consensus using eachof the consensus methods, block combinations having the minimum numberfor each of the plurality of consensus methods. In one or more examples,the computing platform may receive a second asset transfer request.Instead of identifying the consensus method, the computing platform mayexecute, based on the minimum numbers of blocks stored in the governingblock, each of the plurality of consensus methods on the minimum numbersof blocks to establish consensus for the second asset transfer request.

In one or more instances, the governing block may be configured to storea first set of minimum numbers of blocks for a first type of assettransfer requests and a second set of minimum numbers of blocks for asecond type of asset transfer requests. In one or more instances,processing the event may include executing a fund transfer.

In one or more examples, the computing platform may receive a secondasset transfer request. The computing platform may identify, byexecuting each of the plurality of consensus methods, that consensus isnot established for the second asset transfer request. The computingplatform may modify, based on identifying that consensus is notestablished, the stored distributed ledger to include a passive blockrepresenting the second asset transfer request.

In accordance with one or more additional or alternative embodiments ofthe disclosure, a computing platform comprising at least one processor,a communication interface, and memory storing computer-readableinstructions may receive an asset transfer request. The computingplatform may identify a mining cluster for a stored distributed ledger.The computing platform may modify, using the mining cluster, the storeddistributed ledger to include a new block corresponding to the assettransfer request. The computing platform may identify a plurality ofexisting blocks comprising the stored distributed ledger. The computingplatform may identify, for each of a plurality of consensus methods, asubset of the plurality of existing blocks that, when used to performthe corresponding consensus method: 1) uses a minimum number of theplurality of existing blocks to perform the corresponding consensusmethod, and 2) results in a lower energy consumption value than otherpossible subsets of the plurality of existing blocks. The computingplatform may store, in a governing block of the stored distributedledger, block combinations having the minimum number for each of theplurality of consensus methods, and may execute, using eachcorresponding identified subset of the existing blocks, each of theplurality of consensus methods. Based on establishing the consensus, thecomputing platform may send one or more commands directing an eventprocessing platform to process an event corresponding to the assettransfer request, which may cause the event processing platform toprocess the event.

In one or more instances, the computing platform may extract, using deeplearning based optical character recognition (OCR), information from theasset transfer request, where the information may be used to create thenew block. In one or more instances, the information may include one ormore of: a financial institution corresponding to the asset transferrequest, an amount of the asset transfer, a recipient account, or anoriginator account.

In one or more examples, the computing platform may identify, using theinformation and a stored list of authenticated financial institutions,whether or not the financial institution corresponding to the assettransfer request is authenticated. Based on identifying that thefinancial institution corresponding to the asset transfer request is notauthenticated, the computing platform may send an authentication requestto an administrator computing device. Based on identifying that thefinancial institution corresponding to the asset transfer request isauthenticated, the computing platform may proceed to establish whetheror not the asset transfer request is genuine.

In one or more instances, establishing whether or not the asset transferrequest is genuine may include identifying whether or not the originatoraccount includes sufficient assets to perform the asset transfer. In oneor more instances, based on identifying that the asset transfer requestis not genuine, the computing platform may block the asset transfer. Inone or more instances, based on identifying that the asset transferrequest is genuine, the computing platform may generate the new block.

In one or more examples, the computing platform may establish, based onexecution of each of the plurality of consensus methods, the consensusto process the asset transfer request. In one or more examples, theplurality of consensus methods may include one or more of: proof ofwork, proof of stake, proof of elapsed time, raft, proof of importance,proof of authority, proof of activity, proof of capacity, or proof ofburn.

In one or more instances, the computing platform may receive a secondasset transfer request. Instead of identifying the consensus method, thecomputing platform may execute, based on the minimum numbers stored inthe governing block, each of the plurality of consensus methods on theminimum numbers of blocks to establish consensus for the second assettransfer request.

In one or more examples, the governing block may be configured to storea first set of minimum numbers of blocks for a first type of assettransfer requests and a second set of minimum numbers of blocks for asecond type of asset transfer requests. In one or more examples,processing the event may include executing a fund transfer.

In one or more instances, the computing platform may receive a secondasset transfer request. The computing platform may identify, byexecuting each of the plurality of consensus methods, that consensus isnot established for the second asset transfer request. The computingplatform may modify, based on identifying that consensus is notestablished, the stored distributed ledger to include a passive blockrepresenting the second asset transfer request.

These features, along with many others, are discussed in greater detailbelow.

BRIEF DESCRIPTION OF THE DRAWINGS

The present disclosure is illustrated by way of example and not limitedin the accompanying figures in which like reference numerals indicatesimilar elements and in which:

FIGS. 1A-1B depict an illustrative computing environment for anintelligent distributed ledger apparatus for asset transfer inaccordance with one or more example embodiments;

FIGS. 2A-2G depict an illustrative event sequence for an intelligentdistributed ledger apparatus for asset transfer in accordance with oneor more example embodiments;

FIGS. 3 and 5 depict illustrative methods for an intelligent distributedledger apparatus for asset transfer in accordance with one or moreexample embodiments; and

FIG. 4 depicts an illustrative graphical user interface for anintelligent distributed ledger apparatus for asset transfer inaccordance with one or more example embodiments.

DETAILED DESCRIPTION

In the following description of various illustrative embodiments,reference is made to the accompanying drawings, which form a parthereof, and in which is shown, by way of illustration, variousembodiments in which aspects of the disclosure may be practiced. In someinstances, other embodiments may be utilized, and structural andfunctional modifications may be made, without departing from the scopeof the present disclosure.

It is noted that various connections between elements are discussed inthe following description. It is noted that these connections aregeneral and, unless specified otherwise, may be direct or indirect,wired or wireless, and that the specification is not intended to belimiting in this respect.

As a brief introduction to the concepts described below, systems andmethods for using a distributed ledger to manage asset transfer servicesare described herein. More specifically, asset transition services (ATS)operations teams deal in transfers of securities and cash throughautomated customer account transfers (ACAT), non-ACAT transfers(manual), annuity broker dealer and ownership changes, mutual fundtransfers, and transfer paperwork requirements. It may act as abroker/dealer assisting with the transfer of client's incoming andoutgoing assets. In the case of an erroneous delivery in or out ofmachine learning, ATS may perform reclaim activities where accounts arecorrected.

Associates may review paperwork to validate transfers, notifying of anydiscrepancies/missing information through system messages in machinelearning transfer systems emails or phone calls. Decisions of validationor rejection of the transfer request may lead to the followingproblems: 1) authenticity of a customer/asset transfer and securitiesmanipulation, 2) non-association of smaller financial institutions withthe network, 3) interbank communication and cumbersome follow upprocesses, 4) lack of end to end data tracking mechanisms, 5) dealingwith multiple data inputs for transfer requests, 6) potential revenueloss due to incorrect delivery, and 7) manual efforts in processingdocuments/paperwork for asset transfer.

Accordingly, proposed herein is a solution to the above describedproblems that includes creating a blockchain based solution throughwhich asset transfer may happen seamlessly. For example, a hybridbagging consensus mechanism may be used to optimize energy in theblockchain using simulation of a combination of different nodes withvarious consensus methods. Additionally, consensus may be establishedamong different parties to provide the ability to associate non-memberbanks within the blockchain. This may provide effective and efficientdata tracking through the blockchain. In some instances, multiplechannels may be leveraged to receive transfer requests to channelize theintake layer. Using computer vision and/or deep learning mechanisms,information may be validated and extracted for authentication.

As a result, the following benefits may be achieved: 1) optimized energyin the entire blockchain network using the best consensus, 2) seamlessauthentication and communication between financial institutions viablock chain nodes, 3) facilitating addition of new smaller financialinstitutions in the asset transfer platform, 4) elimination of risk withflow of customer information via a distributed digital database securednetwork, and/or 5) channelizing requests via multiple modes toefficiently reduce the cycle time for asset transfer.

Accordingly, described herein is a system that employs the use of hybridbagging consensus mechanisms to optimize energy in the blockchain usingsimulation of combinations of different nodes with various consensusmethods, and that generalizes the model basis simulation of similarcombinations of nodes and consensus.

FIGS. 1A-1B depict an illustrative computing environment for anintelligent distributed ledger apparatus for asset transfer inaccordance with one or more example embodiments. Referring to FIG. 1A,computing environment 100 may include one or more computer systems. Forexample, computing environment 100 may include asset management platform102, client device 103, administrator computing device 104, and eventprocessing platform 105.

As described further below, asset management platform 102 may be acomputer system that includes one or more computing devices (e.g.,servers, server blades, or the like) and/or other computer components(e.g., processors, memories, communication interfaces) that may adistributed ledger and optimization techniques for asset transferrequests.

Client device 103 may be a laptop computer, desktop computer, mobiledevice, tablet, smartphone, or the like that may be used by anindividual to request an asset transfer (e.g., a transfer of funds,stocks, and/or other assets between accounts hosted by differentfinancial institutions). For example, the client device 103 may beoperated by an individual such as a customer of a financial institution,an accountant, a financial advisor, and/or other individual. Forexample, the client device 103 may be used by one or more individuals toaccess a mobile application (e.g., a trading application, mobile bankingapplication, or other application), a website (e.g., an online tradingportal, online banking portal, and/or other website) and/or performother functions. In some instances, client device 103 may be configuredto display one or more user interfaces (e.g., interfaces that enableasset transfer requests, provide notification of event processing,and/or display other information).

Administrator computing device 104 may be a laptop computer, desktopcomputer, mobile device, tablet, smartphone, or the like that may beused by an employee of an enterprise organization (e.g., a financialinstitution, or the like). For example, the administrator computingdevice 104 may be used by one or more individuals to perform one or moretasks, process events, and/or perform other functions. Morespecifically, the administrator computing device 104 may be configuredto maintain a list of registered/approved financial institutions thatmay participate in asset transfers. In some instances, administratorcomputing device 104 may be configured to approve new financialinstitutions and add them to the list.

Event processing platform 105 may be a computer system that includes oneor more computing devices (e.g., servers, server blades, or the like)and/or other computer components (e.g., processors, memories,communication interfaces) that may be configured to process events basedon commands or direction from the asset management platform 102. Forexample, the event processing platform 105 may be configured to processa fund transfer, stock transfer, and/or other asset transfer betweenaccounts.

Computing environment 100 also may include one or more networks, whichmay interconnect asset management platform 102, client device 103,administrator computing device 104, and event processing platform 105.For example, computing environment 100 may include a network 101 (whichmay interconnect, e.g., asset management platform 102, client device103, administrator computing device 104, and/or event processingplatform 105).

In one or more arrangements, asset management platform 102, clientdevice 103, administrator computing device 104, and/or event processingplatform 105 may be any type of computing device capable of sendingand/or receiving requests and processing the requests accordingly. Forexample, asset management platform 102, client device 103, administratorcomputing device 104, event processing platform 105, and/or the othersystems included in computing environment 100 may, in some instances, beand/or include server computers, desktop computers, laptop computers,tablet computers, smart phones, or the like that may include one or moreprocessors, memories, communication interfaces, storage devices, and/orother components. As noted above, and as illustrated in greater detailbelow, any and/or all of asset management platform 102, client device103, administrator computing device 104, and/or event processingplatform 105, may, in some instances, be special-purpose computingdevices configured to perform specific functions.

Referring to FIG. 1B, asset management platform 102 may include one ormore processors 111, memory 112, and communication interface 113. A databus may interconnect processor 111, memory 112, and communicationinterface 113. Communication interface 113 may be a network interfaceconfigured to support communication between asset management platform102 and one or more networks (e.g., network 101, or the like). Memory112 may include one or more program modules having instructions thatwhen executed by processor 111 cause asset management platform 102 toperform one or more functions described herein and/or one or moredatabases that may store and/or otherwise maintain information which maybe used by such program modules and/or processor 111. In some instances,the one or more program modules and/or databases may be stored by and/ormaintained in different memory units of asset management platform 102and/or by different computing devices that may form and/or otherwisemake up asset management platform 102. For example, memory 112 may have,host, store, and/or include asset management module 112 a, assetmanagement database 112 b, and machine learning engine 112 c.

Asset management module 112 a may have instructions that direct and/orcause asset management platform 102 to execute advanced techniques forasset transfer management. Asset management database 112 b may storeinformation used by asset management module 112 a and/or assetmanagement platform 102 in application of advanced distributed ledgermanagement techniques for asset transfer processing, and/or inperforming other functions. Machine learning engine 112 c may haveinstructions that direct and/or cause the asset management platform 102to set, define, and/or iteratively refine optimization rules and/orother parameters used by the asset management platform 102 and/or othersystems in computing environment 100.

FIGS. 2A-2G depict an illustrative event sequence for an intelligentdistributed ledger apparatus for asset transfer in accordance with oneor more example embodiments. Referring to FIG. 2A, at step 201, theclient device 103 may receive an asset transfer request. For example,the client device 103 may receive a request to transfer one or moreassets (e.g., funds, stocks, and/or other assets) from an accountcorresponding to a first financial institution to an accountcorresponding to a second, different financial institution (e.g., not aninternal transfer). In some instances, the client device 103 may receivethe asset transfer request via a mobile application, a website, or othermethod from an individual such as a customer, accountant, financialadvisor, or other individual.

At step 202, the client device 103 may establish a connection with assetmanagement platform 102. For example, the client device 103 mayestablish a first wireless data connection with the asset managementplatform 102 to link the client device 103 to the asset managementplatform 102 (e.g., in preparation for sending the asset transferrequest). In some instances, the client device 103 may identify whetheror not a connection is already established with the asset managementplatform 102. If a connection is already established with the assetmanagement platform 102, the client device 103 might not re-establishthe connection. If a connection is not yet established with the assetmanagement platform 102, the client device 103 may establish the firstwireless data connection as described herein.

At step 203, the client device 103 may send the asset transfer request.For example, the client device 103 may send the asset transfer requestwhile the first wireless data connection is established.

At step 204, the asset management platform 102 may receive the assettransfer request sent at step 203. For example, the asset managementplatform 102 may receive the asset transfer request via thecommunication interface 113 and while the first wireless data connectionis established. In some instances, in receiving the asset transferrequest, the asset management platform 102 may receive an electronicform that includes information related to the asset transfer request.

At step 205, the asset management platform 102 may extract informationfrom the asset transfer request (e.g., from the electronic form). Forexample, the asset management platform 102 may perform deep learningoptical character recognition (OCR) to extract the information. In someinstances, the asset management platform 102 may extract all or aportion of the information included in the asset transfer request. Forexample, the asset management platform 102 may extract one or more of:an originator financial institution corresponding to the asset transferrequest, a recipient financial institution corresponding to the assettransfer request, an amount of the asset transfer (e.g., an amount offunds, quantity of stocks, or the like), a recipient account, anoriginator account, and/or other information that may be used to verifyand/or perform the requested asset transfer. In some instances, theasset management platform 102 may be a cloud based computing platformand/or may otherwise communicate with a cloud based computing platformto store the extracted information in the cloud.

Referring to FIG. 2B, at step 206, the asset management platform 102 mayidentify whether or not the financial institutions (e.g., the originatorand/or the recipient) corresponding to the asset transfer request areauthenticated. For example, the asset management platform 102 maymaintain a stored list of financial institutions that are authenticated(e.g., by a federal agency or other method), and may compare thefinancial institutions to the list. If the asset management platform 102identifies that both financial institutions are authenticated, the assetmanagement platform 102 may proceed to step 213 in FIG. 2C. If the assetmanagement platform 102 identifies that one or more of the financialinstitutions corresponding to the asset transfer request are notauthenticated, the asset management platform 102 may proceed to step207.

At step 207, the asset management platform 102 may establish aconnection with the administrator computing device 104. For example, theasset management platform 102 may establish a second wireless dataconnection with the administrator computing device 104 to link the assetmanagement platform 102 to the administrator computing device 104 (e.g.,in preparation for sending an authentication request). In someinstances, the asset management platform 102 may identify whether or nota connection is already established with the administrator computingdevice 104. If a connection is already established with theadministrator computing device 104, the asset management platform 102might not re-establish the connection. If a connection is not yetestablished with the administrator computing device 104, the assetmanagement platform 102 may establish the second wireless dataconnection as described herein.

At step 208, the asset management platform 102 may send anauthentication request to the administrator computing device 104,requesting that one or more of the financial institutions correspondingto the asset transfer request be authenticated. For example, the assetmanagement platform 102 may send the authentication request to theadministrator computing device 104 via the communication interface 113and while the second wireless data connection is established.

At step 209, the administrator computing device 104 may receive theauthentication request sent at step 208. For example, the administratorcomputing device 104 may receive the authentication request while thesecond wireless data connection is established.

At step 210, the administrator computing device 104 may authenticate thefinancial institution. For example, the administrator computing device104 may communicate with one or more computing systems corresponding toa federal agency and/or perform other techniques to authenticate thefinancial institution. For example, the administrator computing device104 may verify that the financial institution is a valid entity and isreputable for purposes of engaging in the requested asset transfer.

Referring to FIG. 2C, at step 211, if the administrator computing device104 successfully authenticates the financial institution, it mayregister the financial institution so as to add the financialinstitution to the stored list of authenticated financial institutions.In these instances, the administrator computing device 104 may generatea private key corresponding to the financial institution that may beused by the asset management platform 102 to authenticate futurerequests involving the financial institution. If the administratorcomputing device 104 identifies that the financial institution is notauthenticated, it may proceed to step 212 without adding the financialinstitution to the list of authenticated financial institutions (andmay, in some instances, add the financial institution instead to a listof prohibited financial institutions).

At step 212, the administrator computing device 104 may communicate withthe asset management platform 102 to notify the asset managementplatform 102 of the authenticated financial institution (e.g., and theasset management platform 102 may add the stored list of authenticatedfinancial institutions). If the administrator computing device 104identifies that the financial institution is not authenticated, it maynotify the asset management platform 102 that the asset transfer requestshould not be executed.

At step 213, the asset management platform 102 may establish whether ornot the asset transfer request is genuine. For example, the assetmanagement platform 102 may use the information extracted at step 205 toidentify whether the originator account includes sufficient assets toperform the transfer request. For example, the asset management platform102 may compare the assets of the originator account with the assetsrequested to be transferred. If the assets of the originator account aresufficient to perform the transfer, the asset management platform 102may identify that the asset transfer request is genuine, and may proceedto step 215 in FIG. 2D. If the assets of the originator account areinsufficient to perform the transfer, the asset management platform 102may identify that the asset transfer request is not genuine, and mayproceed to step 214.

At step 214, the asset management platform 102 may block the requestedasset transfer. For example, the asset management platform 102 mayprevent the requested assets from being transferred from the originatoraccount to the target recipient account.

Referring to FIG. 2D, at step 215, the asset management platform 102 mayidentify a mining cluster for a stored distributed ledger. In someinstances, the asset management platform 102 may have previouslyidentified the mining cluster (e.g., before receipt of the assettransfer request). For example, the asset management platform 102 mayhave generated the distributed ledger prior to receipt of the assettransfer request at step 201, and may have then stored the distributedledger for use in processing the asset transfer request. However, forillustrative purposes, identification of the mining cluster is describedat this point in the event sequence.

To do so, the asset management platform 102 may access a knowledgebasethat may include an optimal number of computational resources that maybe used to mine the distributed ledger (e.g., the number ofcomputational resources that may balance maximizing accuracy whileminimizing the number of resources used).

At step 216, the asset management platform 102 may generate a new blockfor the distributed ledger. For example, the asset management platform102 may use the extracted information and the mining cluster to generatethe block. In some instances, the asset management platform 102 maycompute a hash of a previous block in the distributed ledger, andinclude the hash in the new block. Once the new block is generated, theasset management platform 102 may modify the distributed ledger toinclude the new block.

At step 217, the asset management platform 102 may identify a consensusmethod for use in verifying that the asset transfer request should beprocessed. For example, rather than selecting a single consensus methodand applying that method to all blocks of the distributed ledger (whichmight not result in the most accurate consensus) or applying everyconsensus method of a plurality of consensus methods to every block ofthe distributed ledger, the asset management platform 102 may use anoptimizer to identify a most efficient consensus method. For example,the asset management platform 102 may use the optimizer to identify aminimum number of blocks to which each of a plurality of consensusmethods may be applied (e.g., a first minimum number for a firstconsensus method, a second minimum number for the second consensusmethod, or the like), while still yielding an accurate result. To do so,the asset management platform 102 may identify, for each of a pluralityof consensus methods, each block in the distributed ledger that hasinformation related to each consensus method, perform random sampling,and/or use other techniques to identify these minimum numbers. In doingso, the asset management platform 102 may use a hybrid bagging consensusmethod to identify an optimal combination of particular consensusmethods applied to particular blocks of the distributed ledger whileminimizing processing resources/energy usage (e.g., because consensusneed not be determined between all blocks, but rather simply a subset).For example, the asset management platform 102 may identify, for each ofa plurality of consensus methods, a subset of blocks from thedistributed ledger that, when used to execute the correspondingconsensus method, result in a lowest energy consumption value incomparison to remaining subsets of blocks. In some instances, the assetmanagement platform 102 may first determine the minimum number of blocksto achieve consensus for each consensus method, and then may perform,for each consensus method, a bagging method to identify a sample set ofblocks that complies with the corresponding minimum number for eachparticular consensus method.

For example, the asset management platform 102 may identify that thedistributed ledger includes blocks 1-5. In this example, the assetmanagement platform 102 may identify that a first consensus methodshould be applied to blocks 1, 2, and 4, whereas a second consensusmethod should be applied to blocks 3 and 4. In this example, performingthe first consensus method using blocks 1, 2, and 4 may consume lessenergy and/or computing resources than, for example, if the firstconsensus method were to be applied to blocks 2, 3, and 5.

With regard to the plurality of consensus methods, the asset managementplatform 102 may identify a minimum number of blocks to which to applyproof of work, proof of state, proof of elapsed time, raft, proof ofimportance, proof of authority, proof of activity, proof of capacity,proof of burn, and/or other consensus methods. In some instances theasset management platform 102 may apply a subset of the consensusmethods (e.g., rather than applying every method).

After identifying the minimum number of blocks for each consensusmethod, the asset management platform 102 may store these minimumnumbers, along with block combinations having the minimum number foreach of the plurality of consensus methods, in a governing block of thedistributed ledger. For example, in some instances, the asset managementplatform 102 may store simulations of combinations having a minimumnumber of different nodes tested/modelled with each of the consensusmethods. In doing so, the asset management platform 102 may access theminimum numbers without repeating the optimization processes describedat step 217 each time a new block is added. For example, if a secondasset transfer request were to be received, rather than performing theoptimization/method selection described above, the asset managementplatform 102 may simply consult the governing block to identify minimumnumbers of blocks to which each consensus method should be applied(e.g., and subsequently execute, using each corresponding identifiedsubset of the existing blocks, each of the plurality of consensusmethods). Nevertheless, in some instances, the asset management platform102 may periodically update the governing block (e.g., as new blocks areadded to the distributed ledger, as new consensus methods areestablished, and/or for other reasons) so as to maintain optimization ofthe consensus method. In some instances, the asset management platform102 may store different minimum numbers in the governing block (or inanother governing block) corresponding to different use cases. Forexample, the asset management platform 102 may identify and store firstnumbers for fund transfers, and second number for stock transfers (ortransfer of other types of assets).

At step 218, the asset management platform 102 may use the identifiedconsensus method from step 217 to identify whether or not consensus isestablished, among the distributed ledger, for the new block. Forexample, the asset management platform 102 may apply each consensusmethod to the corresponding identified subset of blocks in thedistributed ledger (e.g., which may be the minimum number of blocksidentified for each consensus method). This may result in the assetmanagement platform 102 generating a value of “consensus achieved” or“consensus not achieved” (or something to that effect). This methoddescribed in steps 216-218 is further illustrated with regard to FIG. 5, which is described below.

Referring to FIG. 2E, at step 219, the asset management platform 102 mayidentify whether or not the consensus was accepted. For example, if theconsensus was accepted (e.g., consensus achieved), the asset managementplatform 102 may proceed to step 221. In contrast, if the consensus wasnot accepted (e.g., no consensus), the asset management platform 102 mayproceed to step 220.

At step 220, the asset management platform 102 may add a passive block,corresponding to the requested asset transfer, to the distributedledger. In doing so, the asset management platform 102 may add a blockthat indicates the attempt to perform the requested asset transfer forrecord keeping purposes, but might not actually process the requestedasset transfer, and thus might not include processing information in theblock. In these instances, the asset management platform 102 may includeinformation in the block indicating that consensus was not achieved forthe requested asset transfer. Subsequently, the event sequence may end.

At step 221, the asset management platform 102 may add a regular blockto the distributed ledger. For example, the asset management platform102 may add a block indicating that consensus was achieved and, in someinstances, may include processing information for the requested assettransfer.

At step 222, the asset management platform may establish a connectionwith the event processing platform 105. For example, the assetmanagement platform 102 may establish a third wireless data connectionwith the event processing platform 105 to link the asset managementplatform 102 to the event processing platform 105 (e.g., in preparationfor sending an event processing request). In some instances, the assetmanagement platform 102 may identify whether or not a connection isalready established with the event processing platform 105. If aconnection is already established with the event processing platform105, the asset management platform 102 might not re-establish theconnection with the event processing platform 105. If a connection isnot yet established with the event processing platform 105, the assetmanagement platform 102 may establish the third wireless data connectionas described herein.

Referring to FIG. 2F, at step 223, based on or in response toestablishing the consensus, the asset management platform 102 may sendone or more commands directing the event processing platform 105 toprocess an event. For example, the asset management platform 102 maysend a request to process the requested asset transfer (e.g., transferfunds, stocks, and/or other assets). In some instances, the assetmanagement platform 102 may send the event processing request to theevent processing platform 105 via the communication interface 113 andwhile the third wireless data connection is established.

At step 224, the event processing platform 105 may receive the one ormore event processing commands sent at step 223. For example, the eventprocessing platform 105 may receive the event processing request whilethe third wireless data connection is established.

At step 225, based on or in response to the one or more commands, theevent processing platform 105 may process the event corresponding to theasset transfer request. For example, the event processing platform 105may transfer funds, stocks, and/or other assets from the originatoraccount to the recipient account specified in the asset transferrequest. In some instances, the event processing platform 105 may deductone or more assets (e.g., on behalf of a processing entity, financialinstitution, or the like) from the total amount of assets beingtransferred prior to processing the event.

At step 226, the event processing platform 105 may establish aconnection with the client device 103. For example, the event processingplatform 105 may establish a fourth wireless data connection with theclient device 103 to link the event processing platform 105 to theclient device 103 (e.g., in preparation for sending event processingconfirmation information). For example, the event processing platform105 may identify whether or not a connection is already established withthe client device 103. If a connection is already established with theclient device 103, the event processing platform 105 might notre-establish the connection. If a connection is not yet established withthe client device 103, the event processing platform 105 may establishthe fourth wireless data connection as described herein.

At step 227, the event processing platform 105 may send event processingconfirmation information indicating that the asset transfer request hasbeen satisfied. In some instances, the event processing platform 105 mayalso send one or more commands directing the client device 103 todisplay the event processing confirmation information. In someinstances, the event processing platform 105 may send the eventprocessing confirmation information while the fourth wireless dataconnection is established.

At step 228, the client device 103 may receive the event processingconfirmation information. In some instances, the client device 103 mayalso receive the one or more commands directing the client device 103 todisplay the event processing confirmation information. In someinstances, the client device 103 may receive the event processingconfirmation information while the fourth wireless data connection isestablished.

Referring to FIG. 2G, at step 229, based on or in response to the one ormore commands directing the client device 103 to display the eventprocessing confirmation information, the client device 103 may displaythe event processing confirmation information. For example, the clientdevice 103 may display a graphical user interface similar to graphicaluser interface 405, which is illustrated in FIG. 4 , and that providesconfirmation that the requested asset transfer has been successfullycompleted.

FIG. 3 depicts an illustrative method for an intelligent distributedledger apparatus for asset transfer in accordance with one or moreexample embodiments. Referring to FIG. 3 , at step 305, a computingplatform having at least one processor, a communication interface, andmemory may receive an asset transfer request. At step 310, the computingplatform may extract information from the asset transfer request. Atstep 315, the computing platform may identify whether or not a financialinstitution corresponding to the asset transfer request isauthenticated. If the financial institution is authenticated, thecomputing platform may proceed to step 330. If the financial institutionis not authenticated, the computing platform may proceed to step 320.

At step 320, the computing platform may send an authentication requestto an administrator computing device. At step 325, the computingplatform may receive notification of registration of the financialinstitution.

At the 330, the computing platform may identify whether or not the assettransfer request is genuine. If the asset transfer request is notgenuine, the computing platform may proceed to step 335. At step 335,the computing platform may block the requested asset transfer, and themethod may end.

Returning to step 330, if the asset transfer request is genuine, thecomputing platform may proceed to step 340. At step 340, the computingplatform may identify a mining cluster for a distributed ledger. At step345, the computing platform may use the mining cluster to generate a newblock in the distributed ledger corresponding to the requested assettransfer. At step 350, the computing platform may identify a consensusmethod for the distributed ledger. At step 355, the computing platformmay use the consensus method to establish consensus. At step 360, thecomputing platform may identify whether or not consensus was achieved.If consensus was not achieved, the computing platform may proceed tostep 365. At step 365, the computing platform may add a passive block tothe distributed ledger representing the failed asset transfer request,and the method may end.

Returning to step 360, if consensus was achieved, the computing platformmay proceed to step 370. At step 370, the computing platform may add aregular block to the distributed ledger representing the successfulasset transfer request. At step 375, the computing platform may send anevent processing request directing an event processing platform toprocess an asset transfer corresponding to the request.

FIG. 5 depicts an illustrative method for an intelligent distributedledger apparatus for asset transfer in accordance with one or moreexample embodiments. At step 505, a computing platform having at leastone processor, a communication interface, and memory may generate ablock (e.g., a block corresponding to an asset transfer request). Atstep 510, the computing platform may receive a request to obtainconsensus from a distributed ledger for the block. At step 515, thecomputing platform may identify whether or not a consensus method isaccessible from a governing block of the distributed ledger (e.g., apreviously identified consensus method for energy optimization). If so,the computing platform may proceed to step 525 and perform the optimalenergy consensus method to identify whether or not consensus is achievedwith regard to the new block. If not, the computing platform may proceedto step 520, and may use an optimizer to identify consensus method forenergy optimization. For example, as described above with regard to step217, the computing platform may identify a minimum number of blocks inthe distributed ledger to which each of a plurality of consensus methodsshould be applied. The computing platform may then proceed to step 525to apply each of the plurality of consensus methods to a number ofblocks (which may be selected through a bagging process) equal to thecorresponding minimum number of blocks for each consensus method.

One or more aspects of the disclosure may be embodied in computer-usabledata or computer-executable instructions, such as in one or more programmodules, executed by one or more computers or other devices to performthe operations described herein. Generally, program modules includeroutines, programs, objects, components, data structures, and the likethat perform particular tasks or implement particular abstract datatypes when executed by one or more processors in a computer or otherdata processing device. The computer-executable instructions may bestored as computer-readable instructions on a computer-readable mediumsuch as a hard disk, optical disk, removable storage media, solid-statememory, RAM, and the like. The functionality of the program modules maybe combined or distributed as desired in various embodiments. Inaddition, the functionality may be embodied in whole or in part infirmware or hardware equivalents, such as integrated circuits,application-specific integrated circuits (ASICs), field programmablegate arrays (FPGA), and the like. Particular data structures may be usedto more effectively implement one or more aspects of the disclosure, andsuch data structures are contemplated to be within the scope of computerexecutable instructions and computer-usable data described herein.

Various aspects described herein may be embodied as a method, anapparatus, or as one or more computer-readable media storingcomputer-executable instructions. Accordingly, those aspects may takethe form of an entirely hardware embodiment, an entirely softwareembodiment, an entirely firmware embodiment, or an embodiment combiningsoftware, hardware, and firmware aspects in any combination. Inaddition, various signals representing data or events as describedherein may be transferred between a source and a destination in the formof light or electromagnetic waves traveling through signal-conductingmedia such as metal wires, optical fibers, or wireless transmissionmedia (e.g., air or space). In general, the one or morecomputer-readable media may be and/or include one or more non-transitorycomputer-readable media.

As described herein, the various methods and acts may be operativeacross one or more computing servers and one or more networks. Thefunctionality may be distributed in any manner, or may be located in asingle computing device (e.g., a server, a client computer, and thelike). For example, in alternative embodiments, one or more of thecomputing platforms discussed above may be combined into a singlecomputing platform, and the various functions of each computing platformmay be performed by the single computing platform. In such arrangements,any and/or all of the above-discussed communications between computingplatforms may correspond to data being accessed, moved, modified,updated, and/or otherwise used by the single computing platform.Additionally or alternatively, one or more of the computing platformsdiscussed above may be implemented in one or more virtual machines thatare provided by one or more physical computing devices. In sucharrangements, the various functions of each computing platform may beperformed by the one or more virtual machines, and any and/or all of theabove-discussed communications between computing platforms maycorrespond to data being accessed, moved, modified, updated, and/orotherwise used by the one or more virtual machines.

Aspects of the disclosure have been described in terms of illustrativeembodiments thereof. Numerous other embodiments, modifications, andvariations within the scope and spirit of the appended claims will occurto persons of ordinary skill in the art from a review of thisdisclosure. For example, one or more of the steps depicted in theillustrative figures may be performed in other than the recited order,and one or more depicted steps may be optional in accordance withaspects of the disclosure.

What is claimed is:
 1. A computing platform comprising: at least oneprocessor; a communication interface communicatively coupled to the atleast one processor; and memory storing computer-readable instructionsthat, when executed by the at least one processor, cause the computingplatform to: identify, for a stored distributed ledger, an overallconsensus method, wherein identifying the overall consensus methodcomprises: identifying, for each of a plurality of consensus methods andusing a hybrid bagging approach comprising random sampling and a baggingmethod, a minimum number of blocks needed to establish consensus using acorresponding consensus method, wherein identifying the minimum numberof blocks comprises, for each corresponding consensus method:identifying related information comprising information used to executethe corresponding consensus method, identifying blocks of the storeddistributed ledger that include the related information, identifying,using the random sampling, the minimum number of blocks, and selecting,using the bagging method, a subset of the blocks of the storeddistributed ledger that include the related information, wherein thesubset of the blocks corresponds to the minimum number of blocks;execute each of the plurality of consensus methods using thecorresponding identified blocks, wherein executing each of the pluralityof consensus methods using the minimum number of blocks consumes lessprocessing power than executing each of the plurality of consensusmethods using all blocks of the stored distributed ledger, and whereinexecuting each of the plurality of consensus methods rather than asingle consensus method increases a level of security corresponding toasset transfer requests; based on establishing consensus, using each ofthe plurality of consensus methods, to process an asset transferrequest, send one or more commands directing an event processingplatform to process an event corresponding to the asset transferrequest, wherein sending the one or more commands directing the eventprocessing platform to process the event corresponding to the assettransfer request causes the event processing platform to process theevent; and store, in a governing block of the stored distributed ledger,and for each of the consensus methods: the corresponding minimum numberof blocks; and subsets of the blocks of the stored distributed ledgerthat include the related information, wherein: each subset correspondsto the minimum number of blocks, and storage of the minimum number ofblocks in the governing block optimizes energy usage associated withidentifying future overall consensus methods.
 2. The computing platformof claim 1, wherein the information includes one or more of: a financialinstitution corresponding to the asset transfer request, an amount ofthe asset transfer, a recipient account, or an originator account. 3.The computing platform of claim 2, wherein the memory stores additionalcomputer-readable instructions that, when executed by the at least oneprocessor, cause the computing platform to: identify, using theinformation and a stored list of authenticated financial institutions,whether or not the financial institution corresponding to the assettransfer request is authenticated; based on identifying that thefinancial institution corresponding to the asset transfer request is notauthenticated, send an authentication request to an administratorcomputing device; and based on identifying that the financialinstitution corresponding to the asset transfer request isauthenticated, proceed to establish whether or not the asset transferrequest is genuine.
 4. The computing platform of claim 3, whereinestablishing whether or not the asset transfer request is genuinecomprises identifying whether or not the originator account includessufficient assets to perform the asset transfer.
 5. The computingplatform of claim 4, wherein the memory stores additionalcomputer-readable instructions that, when executed by the at least oneprocessor, cause the computing platform to: based on identifying thatthe asset transfer request is not genuine, block the asset transfer; andbased on identifying that the asset transfer request is genuine, performgeneration of a new block corresponding to the asset transfer request.6. The computing platform of claim 1, wherein the plurality of consensusmethods includes one or more of: proof of work, proof of stake, proof ofelapsed time, raft, proof of importance, proof of authority, proof ofactivity, proof of capacity, or proof of burn.
 7. The computing platformof claim 1, wherein the governing block is configured to store a firstset of minimum numbers of blocks for a first type of asset transferrequests and a second set of minimum numbers of blocks for a second typeof asset transfer requests.
 8. The computing platform of claim 1,wherein processing the event comprises executing a fund transfer.
 9. Thecomputing platform of claim 1, wherein the memory stores additionalcomputer-readable instructions that, when executed by the at least oneprocessor, cause the computing platform to: receive a second assettransfer request; identify, by executing each of the plurality ofconsensus methods, that consensus is not established for the secondasset transfer request; and modify, based on identifying that consensusis not established, the stored distributed ledger to include a passiveblock representing the second asset transfer request.
 10. The computingplatform of claim 1, wherein memory stores additional computer-readableinstructions that, when executed by the at least one processor, causethe computing platform to: receive, after the asset transfer request, asecond asset transfer request; identify the overall consensus method,wherein identifying the overall consensus method comprises: accessing,for each of the consensus methods and from the governing block, thecorresponding subsets of the blocks of the stored distributed ledgerthat include the related information; and execute each of the pluralityof consensus methods using the corresponding subsets of blocks.
 11. Thecomputing platform of claim 1, wherein memory stores additionalcomputer-readable instructions that, when executed by the at least oneprocessor, cause the computing platform to: receive the asset transferrequest; extract, using deep learning based optical characterrecognition (OCR), information from the asset transfer request; identifya mining cluster for the stored distributed ledger; and modify, usingthe mining cluster, the stored distributed ledger to include a new blockcorresponding to the asset transfer request.
 12. The computing platformof claim 1, wherein memory stores additional computer-readableinstructions that, when executed by the at least one processor, causethe computing platform to: establish, based on execution of each of theplurality of consensus methods, consensus to process the asset transferrequest.
 13. A method comprising: at a computing platform comprising atleast one processor, a communication interface, and memory: identifying,for a stored distributed ledger, an overall consensus method, whereinidentifying the overall consensus method comprises: identifying, foreach of a plurality of consensus methods and using a hybrid baggingapproach comprising random sampling and a bagging method, a minimumnumber of blocks needed to establish consensus using a correspondingconsensus method, wherein identifying the minimum number of blockscomprises, for each corresponding consensus method: identifying relatedinformation comprising information used to execute the correspondingconsensus method, identifying blocks of the stored distributed ledgerthat include the related information, identifying, using the randomsampling, the minimum number of blocks, and selecting, using the baggingmethod, a subset of the blocks of the stored distributed ledger thatinclude the related information, wherein the subset of the blockscorresponds to the minimum number of blocks; executing each of theplurality of consensus methods using the corresponding identifiedblocks, wherein executing each of the plurality of consensus methodsusing the minimum number of blocks consumes less processing power thanexecuting each of the plurality of consensus methods using all blocks ofthe stored distributed ledger, and wherein executing each of theplurality of consensus methods rather than a single consensus methodincreases a level of security corresponding to asset transfer requests;based on establishing consensus, using each of the plurality ofconsensus methods, to process an asset transfer request, sending one ormore commands directing an event processing platform to process an eventcorresponding to the asset transfer request, wherein sending the one ormore commands directing the event processing platform to process theevent corresponding to the asset transfer request causes the eventprocessing platform to process the event; and storing, in a governingblock of the stored distributed ledger, and for each of the consensusmethods: the corresponding minimum number of blocks; and subsets of theblocks of the stored distributed ledger that include the relatedinformation, wherein: each subset corresponds to the minimum number ofblocks, and storage of the minimum number of blocks in the governingblock optimizes energy usage associated with identifying future overallconsensus methods.
 14. The method of claim 13, wherein the informationincludes one or more of: a financial institution corresponding to theasset transfer request, an amount of the asset transfer, a recipientaccount, or an originator account.
 15. The method of claim 14, furthercomprising: identifying, using the information and a stored list ofauthenticated financial institutions, whether or not the financialinstitution corresponding to the asset transfer request isauthenticated; based on identifying that the financial institutioncorresponding to the asset transfer request is not authenticated,sending an authentication request to an administrator computing device;and based on identifying that the financial institution corresponding tothe asset transfer request is authenticated, proceeding to establishwhether or not the asset transfer request is genuine.
 16. The method ofclaim 15, wherein establishing whether or not the asset transfer requestis genuine comprises identifying whether or not the originator accountincludes sufficient assets to perform the asset transfer.
 17. The methodof claim 16, further comprising: based on identifying that the assettransfer request is not genuine, blocking the asset transfer; and basedon identifying that the asset transfer request is genuine, performinggeneration of a new block corresponding to the asset transfer request.18. The method of claim 13, wherein the plurality of consensus methodsincludes one or more of: proof of work, proof of stake, proof of elapsedtime, raft, proof of importance, proof of authority, proof of activity,proof of capacity, or proof of burn.
 19. The method of claim 13, whereinthe governing block is configured to store a first set of minimumnumbers of blocks for a first type of asset transfer requests and asecond set of minimum numbers of blocks for a second type of assettransfer requests.
 20. One or more non-transitory computer-readablemedia storing instructions that, when executed by a computing platformcomprising at least one processor, a communication interface, andmemory, cause the computing platform to: identify, for a storeddistributed ledger, an overall consensus method, wherein identifying theoverall consensus method comprises: identifying, for each of a pluralityof consensus methods and using a hybrid bagging approach comprisingrandom sampling and a bagging method, a minimum number of blocks neededto establish consensus using a corresponding consensus method, whereinidentifying the minimum number of blocks comprises, for eachcorresponding consensus method: identifying related informationcomprising information used to execute the corresponding consensusmethod, identifying blocks of the stored distributed ledger that includethe related information, identifying, using the random sampling, theminimum number of blocks, and selecting, using the bagging method, asubset of the blocks of the stored distributed ledger that include therelated information, wherein the subset of the blocks corresponds to theminimum number of blocks; execute each of the plurality of consensusmethods using the corresponding identified blocks, wherein executingeach of the plurality of consensus methods using the minimum number ofblocks consumes less processing power than executing each of theplurality of consensus methods using all blocks of the storeddistributed ledger, and wherein executing each of the plurality ofconsensus methods rather than a single consensus method increases alevel of security corresponding to asset transfer requests; based onestablishing consensus, using each of the plurality of consensusmethods, to process an asset transfer request, send one or more commandsdirecting an event processing platform to process an event correspondingto the asset transfer request, wherein sending the one or more commandsdirecting the event processing platform to process the eventcorresponding to the asset transfer request causes the event processingplatform to process the event; and store, in a governing block of thestored distributed ledger, and for each of the consensus methods: thecorresponding minimum number of blocks; and subsets of the blocks of thestored distributed ledger that include the related information, wherein:each subset corresponds to the minimum number of blocks, and storage ofthe minimum number of blocks in the governing block optimizes energyusage associated with identifying future overall consensus methods.